2026-09-27 · class-notes, a-plus, comptia, messer, hardware, bios, uefi, firmware, post, boot
Full class notes for A+ Core 1 3.5: BIOS firmware, POST and boot, legacy BIOS vs UEFI, dual-BIOS flash, and settings.
Class notes · Professor Messer A+ Core 1 (220-1201) · Section 3, lesson 5
Quick reference: the short version of this lesson lives in the A+ Core 1 Section 3 resource sheets. This is a fifth lesson under objective 3.5 ("install and configure motherboards, CPUs, and add-on cards"), joining Motherboard form factors, expansion slots, connections and compatibility. Here we look at the firmware that starts the board before any operating system exists.
By the end of these notes you should be able to:
Press the power button and, for the first few seconds, what fills the screen has nothing to do with the operating system that eventually loads. That early screen is the BIOS — the Basic Input/Output System. You will hear it called by several names: the system's firmware, the system BIOS, or the ROM BIOS, where ROM means Read-Only Memory.
That last name is now a historical hangover. Modern systems do not keep the BIOS in true read-only memory; it lives in flash memory on the motherboard instead, which is what makes it updatable. The BIOS's job is to initialise the system and get everything ready to hand over to the operating system.
Note (beyond this lesson): the BIOS program lives in flash, but your settings (and the real-time clock) are held in a small amount of battery-backed memory kept alive by the motherboard's CR2032 coin cell. A dead cell is the classic cause of a clock that resets and BIOS settings that revert on every power-off.
The start-up sequence you watch is the Power-On Self-Test, or POST. It is a quick diagnostic that checks the core hardware is present and sane: is there a CPU, is memory installed, are a keyboard and mouse connected? If any of those core systems fails to initialise, POST puts an error message on the screen rather than pressing on.
POST takes only a few seconds. Once it passes, control moves to the bootloader — the point at which the firmware has finished its checks and is ready to load an operating system. Depending on the machine, the OS may start immediately, or you may get a prompt asking which operating system to load. Reaching that prompt is the signal that POST is complete.
Power on
|
v
+----------------------+
| BIOS / UEFI starts | firmware in flash on the board
+----------+-----------+
|
v
+----------------------+
| POST self-test | CPU? RAM? keyboard/mouse?
+----------+-----------+ fail -> error message on screen
| pass
v
+----------------------+
| Bootloader | choose an OS if prompted
+----------+-----------+
|
v
+----------------------+
| Operating system |
+----------------------+
Because the BIOS is in flash on the motherboard, you can often find the chip physically marked on the board. Many boards carry two BIOS flash chips: a main BIOS and a backup. The reason is safety during an update. A BIOS upgrade rewrites the flash, and if that process is interrupted — a power cut, a bad image — the board could be left unbootable. A second, standby copy means you can recover to a known-good BIOS if an upgrade goes wrong.
In the real world: this is why a BIOS/UEFI update is one of the few maintenance jobs where you genuinely do not want to lose power partway. Use a reliable supply, and never interrupt a flash in progress.
On older PCs you may meet a legacy (traditional) BIOS — a design that has been around for more than twenty-five years. If a machine runs an older operating system on older hardware, it is probably using legacy BIOS. The catch is that legacy BIOS was written for older, legacy hardware, so putting newer hardware into an old system can run into a legacy BIOS that simply does not support it.
A legacy BIOS presents a text-based screen. You navigate it from the keyboard — arrow keys to move, and Enter, Space or various function keys to select and change values — with the available choices listed along the bottom of each screen so you always know your options.
Correction: the transcript describes the legacy screen as one you move around with "mouse keys". Legacy BIOS is keyboard-navigated and has no mouse support — mouse control is a UEFI feature (below). The keyboard keys the transcript then lists (Enter, Space, function keys) are the correct ones.
Note (beyond this lesson): legacy BIOS pairs with MBR partitioning, which brings the familiar limits — up to four primary partitions and a ~2 TB boot-disk ceiling. UEFI pairs with GPT, which lifts both. That partition detail belongs with the Operating systems material, but it is the practical reason legacy vs UEFI matters at install time.
Modern hardware needs a modern firmware, and on a recent computer that is a UEFI BIOS. UEFI stands for Unified Extensible Firmware Interface, a standard created by Intel and now used on essentially all modern systems.
Because UEFI is a standard, its functionality is broadly consistent across manufacturers — the options and features look and behave much the same whoever built the machine. It also brings a friendlier interface: graphical screens you can drive with a mouse, not just the keyboard.
The settings a UEFI interface exposes are the ones you would expect for bringing a machine up to the point of loading an OS:
Note (beyond this lesson): UEFI grew out of Intel's earlier EFI and is now maintained by the multi-vendor UEFI Forum, which is why the experience is so similar across brands. UEFI also enables Secure Boot, which pairs with a TPM in the modern trusted-boot stack.
A user needs to run virtual machines, and the hypervisor complains that hardware virtualisation is off.
The discipline the lesson stresses: some firmware settings are critical to reliable operation, so back up and document before you change anything, and change only what you understand.
To restate the caution plainly: several BIOS/UEFI settings are critical to whether the system runs reliably at all, so they are not things to change on a hunch. Before any BIOS update or configuration change, make backups and keep documentation of the previous configuration, so you have a route back if the new settings cause trouble.
Firmware runs before and beneath the operating system, which makes the BIOS both a powerful control point and a high-value target:
| Term | Meaning |
|---|---|
| BIOS | Basic Input/Output System; the firmware that starts the board. |
| Firmware | Low-level software stored on the hardware itself. |
| ROM BIOS | Old name; the BIOS is now in flash, not read-only memory. |
| Flash memory | Rewritable storage on the board holding the BIOS. |
| POST | Power-On Self-Test; the start-up hardware check. |
| Bootloader | The stage that loads (or offers a choice of) the OS. |
| Dual BIOS | Main plus backup BIOS chips for safe recovery. |
| Legacy BIOS | Traditional text-based, keyboard-navigated firmware. |
| UEFI | Unified Extensible Firmware Interface; the modern standard. |
| Secure Boot | UEFI feature that only lets signed boot code run. |
| Virtualisation setting | Advanced CPU option (VT-x / AMD-V) enabling hypervisors. |
| Boot order | The sequence of devices the firmware tries to boot from. |
| Supervisor password | A firmware password protecting BIOS settings. |
| CR2032 | The coin cell backing BIOS settings and the clock. |
| Baseline | The documented known-good firmware version and settings. |